Context data sharing

ABSTRACT

One embodiment provides a method, including: receiving, at an information handling device in a low power mode, a wake indication; waking, responsive to the receiving, the information handling device from the low power mode; receiving, at the awoken information handling device, context data obtained by at least one other device; and performing an action based on the received context data. Other aspects are described and claimed.

BACKGROUND

Various components of many information handling devices (“devices”), forexample smart phones, tablets, stand-alone digital assistants, laptopand personal computers, other electronic devices, and the like, may bealways-on. For example, a device may maintain an audio capture device(e.g., a microphone, etc.) in an always-on state to continuously monitorfor any actionable voice input. As another example, a device maymaintain an image/video capture device (e.g., a camera, etc.) in analways-on state to monitor for a user's presence. Components maintainedin an always-on state must consume a certain amount of the device'sbattery power to function.

BRIEF SUMMARY

In summary, one aspect provides a method, comprising: receiving, at aninformation handling device in a low power mode, a wake indication;waking, responsive to the receiving, the information handling devicefrom the low power mode; receiving, at the awoken information handlingdevice, context data obtained by at least one other device; andperforming an action based on the received context data.

Another aspect provides an information handling device, comprising: aprocessor; a memory device that stores instructions executable by theprocessor to: receive, when the information handling device is in a lowpower mode, a wake indication; wake, responsive to the receiving, theinformation handling device from the low power mode; receiving, at theawoken information handling device, context data obtained by at leastone other device; and perform an action based on the received contextdata.

A further aspect provides a system, comprising: a plurality of connecteddevices configured to transmit context data to an information handlingdevice in a low power mode, wherein the system is configured to: gathercontext data using the plurality of connected devices; wake, responsiveto the gathering, the information handling device from the low powermode; send the context data to the awoken information handling device;and perform, using the information handling device, an action based onthe received context data.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of information handling device circuitry.

FIG. 2 illustrates another example of information handling devicecircuitry.

FIG. 3 illustrates an example method of gathering and processing contextdata using one or more Internet of things (IoT) devices.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearance of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well knownstructures, materials, or operations are not shown or described indetail to avoid obfuscation.

Devices comprising always-on components (e.g., audio capture devices,image/video capture devices, etc.) continuously provide processing powerto these components, even when the components are not being activelyused. In order to prevent a large amount of device power from beingconsumed, the processing responsibilities are generally handled bysmall, low-power microcontrollers associated with each of the always-oncomponents.

Although the microcontrollers do not consume a great deal of batterypower, they still consume some power, which places a measurable drain onthe battery. Additionally, the microcontrollers have limitedperformance/function capabilities and are generally unable to executecomplex tasks (e.g., tasks based on context, etc.). Additionally still,if a device comprises a plurality of always-on components, the batterydrain may be more significant. Furthermore, although a device'salways-on components may be able to gather some context data, they maynot be able to gather the complete context of the surrounding areabecause each of the components has a limited capture range and a limitedcapability to analyze contextual information. For example, a cameralocated on the front of the device may be able to detect motionoccurring in front of it but may be blind to any motion occurring behindit. In a similar example, a microphone of the device may be able tocapture audio within a predetermined range of the device but may not beable to detect any audio outside of the predetermined range (e.g., audiooccurring in another room, etc.)

Accordingly, an embodiment may leverage the functionality of surroundingInternet of Things (IoT) devices to gather context data associated witha device's surroundings and thereafter provide the device with anindication of an appropriate action to take based on the data. In anembodiment, context data (e.g., user position data, object positiondata, ambient light data, other environmental data, etc.) may beobtained by one or more IoT devices. The obtained context data may beprocessed on the IoT devices or may be processed by the cloud, which maycomplex decisions based on IoT input. The gathered context data maythereafter be communicated (e.g., via the cloud, another wirelesstransmission technique, etc.) to a user's device. In an embodiment, theuser's device may be in an energy-saving/lower-power mode (e.g., standbymode, hibernation mode, etc.) while context data is gathered and/orprocessed by the IoT devices. In an embodiment, responsive to receivinga wake indication (e.g., an indication notifying the device thatrelevant context data has been gathered, etc.), the device may be awokenand may thereafter perform an action based on the received context data.Such a method may allow a device to take advantage of more comprehensivecontext analysis without consuming substantially any battery.

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to smart phone and/or tabletcircuitry 100, an example illustrated in FIG. 1 includes a system on achip design found for example in tablet or other mobile computingplatforms. Software and processor(s) are combined in a single chip 110.Processors comprise internal arithmetic units, registers, cache memory,busses, I/O ports, etc., as is well known in the art. Internal bussesand the like depend on different vendors, but essentially all theperipheral devices (120) may attach to a single chip 110. The circuitry100 combines the processor, memory control, and I/O controller hub allinto a single chip 110. Also, systems 100 of this type do not typicallyuse SATA or PCI or LPC. Common interfaces, for example, include SDIO andI2C.

There are power management chip(s) 130, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 140, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 110, is usedto supply BIOS like functionality and DRAM memory.

System 100 typically includes one or more of a WWAN transceiver 150 anda WLAN transceiver 160 for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additionally, devices 120 are commonly included, e.g., an imagesensor such as a camera, audio capture device such as a microphone,motion sensor such as an accelerometer or gyroscope, a thermal sensor,etc. System 100 often includes one or more touch screens 170 for datainput and display/rendering. System 100 also typically includes variousmemory devices, for example flash memory 180 and SDRAM 190.

FIG. 2 depicts a block diagram of another example of informationhandling device circuits, circuitry or components. The example depictedin FIG. 2 may correspond to computing systems such as the THINKPADseries of personal computers sold by Lenovo (US) Inc. of Morrisville,N.C., or other devices. As is apparent from the description herein,embodiments may include other features or only some of the features ofthe example illustrated in FIG. 2.

The example of FIG. 2 includes a so-called chipset 210 (a group ofintegrated circuits, or chips, that work together, chipsets) with anarchitecture that may vary depending on manufacturer (for example,INTEL, AMD, ARM, etc.). INTEL is a registered trademark of IntelCorporation in the United States and other countries. AMD is aregistered trademark of Advanced Micro Devices, Inc. in the UnitedStates and other countries. ARM is an unregistered trademark of ARMHoldings plc in the United States and other countries. The architectureof the chipset 210 includes a core and memory control group 220 and anI/O controller hub 250 that exchanges information (for example, data,signals, commands, etc.) via a direct management interface (DMI) 242 ora link controller 244. In FIG. 2, the DMI 242 is a chip-to-chipinterface (sometimes referred to as being a link between a “northbridge”and a “southbridge”). The core and memory control group 220 include oneor more processors 222 (for example, single or multi-core) and a memorycontroller hub 226 that exchange information via a front side bus (FSB)224; noting that components of the group 220 may be integrated in a chipthat supplants the conventional “northbridge” style architecture. One ormore processors 222 comprise internal arithmetic units, registers, cachememory, busses, I/O ports, etc., as is well known in the art.

In FIG. 2, the memory controller hub 226 interfaces with memory 240 (forexample, to provide support for a type of RAM that may be referred to as“system memory” or “memory”). The memory controller hub 226 furtherincludes a low voltage differential signaling (LVDS) interface 232 for adisplay device 292 (for example, a CRT, a flat panel, touch screen,etc.). A block 238 includes some technologies that may be supported viathe LVDS interface 232 (for example, serial digital video, HDMI/DVI,display port). The memory controller hub 226 also includes a PCI-expressinterface (PCI-E) 234 that may support discrete graphics 236.

In FIG. 2, the I/O hub controller 250 includes a SATA interface 251 (forexample, for HDDs, SDDs, etc., 280), a PCI-E interface 252 (for example,for wireless connections 282), a USB interface 253 (for example, fordevices 284 such as a digitizer, keyboard, mice, cameras, phones,microphones, storage, other connected devices, etc.), a networkinterface 254 (for example, LAN), a GPIO interface 255, a LPC interface270 (for ASICs 271, a TPM 272, a super I/O 273, a firmware hub 274, BIOSsupport 275 as well as various types of memory 276 such as ROM 277,Flash 278, and NVRAM 279), a power management interface 261, a clockgenerator interface 262, an audio interface 263 (for example, forspeakers 294), a TCO interface 264, a system management bus interface265, and SPI Flash 266, which can include BIOS 268 and boot code 290.The I/O hub controller 250 may include gigabit Ethernet support.

The system, upon power on, may be configured to execute boot code 290for the BIOS 268, as stored within the SPI Flash 266, and thereafterprocesses data under the control of one or more operating systems andapplication software (for example, stored in system memory 240). Anoperating system may be stored in any of a variety of locations andaccessed, for example, according to instructions of the BIOS 268. Asdescribed herein, a device may include fewer or more features than shownin the system of FIG. 2.

Information handling device circuitry, as for example outlined in FIG. 1or FIG. 2, may be used in devices such as smart phones, tablets, smartspeakers, televisions, laptop and personal computer devices generally,and/or electronic devices that are capable of connecting with andreceiving communication from other IoT devices. For example, thecircuitry outlined in FIG. 1 may be implemented in a tablet or smartphone embodiment, whereas the circuitry outlined in FIG. 2 may beimplemented in a laptop.

Referring now to FIG. 3, an embodiment may gather various types ofcontext data using one or more IoT devices and thereafter communicatethis data to a device in a low-power mode. In an embodiment, contextdata may be received at a device in a low-power mode. In the context ofthis application, a low power mode may be any device operation modeduring which components of the device consume little to no power (e.g.,sleep mode, hibernation mode, etc.).

In an embodiment, context data may be virtually any type of dataassociated with aspects of the device's surroundings such as a positionof the device, positions of other devices or objects, positions and/oridentities of users, other types of environmental data, etc. In anembodiment, the context data may be collected using one or more datagathering devices (e.g., one or more audio capture devices, imagecapture devices, motion sensing devices, heat and/or light sensingdevices, etc.). In an embodiment, the context data may be data that isnot attainable by the device. For example, the context data may be dataassociated with contextual events occurring in a different room fromwhich the device is positioned. In another example, the context data maybe unattainable by the device because the data gathering components ofthe device may not be able to gather the type of context data beingreceived.

In an embodiment, the context data may be gathered by one or more IoTdevices that may thereafter communicate the context data to the device.In an embodiment, the one or more IoT devices may be of a variety ofdifferent device types (e.g., audio capture devices, video capturedevices, other smart sensing devices, etc.) positioned in variouslocations around the surrounding area (e.g., various positions aroundthe same room as the device, various positions in one or more differentrooms than the room the device is positioned in, etc.).

In an embodiment, the gathered context data may be processed away fromthe device. For example, in an embodiment, each IoT device mayindependently gather and locally process context data. The processedcontext data may be held by each device or shared among the IoT devicesto identify one or more combinations of actionable context data (i.e.,context data indicating a need for a user device to perform an action).Additionally or alternatively, if one or more of the IoT devices areconnected to a cloud-based server, the cloud server may do some or allof the data processing. Responsive to at least one IoT device and/orconnected server identifying actionable context data, a transmission maybe sent to the user device comprising an instruction to wake up and/oralso comprising the relevant context data and/or the suggested action.The transmission may be communicated to the user device using a wirelesstransmission technique (e.g., BLUETOOTH, PAN, WLAN, WAN, anotherwireless protocol, etc.). As an example of the foregoing, responsive toan IoT device identifying that a user is approaching a user device(e.g., a laptop, etc.), the IoT device may send a communication to thelaptop to wake up from its low power mode and activate a display screenof the device.

At 301, the user device may receive a wake indication prompting thedevice to wake from the low power mode. In an embodiment, the wakeindication may be sent to the user device by the IoT device or cloudserver and may either be a dedicated wake indication (i.e., atransmission sent solely to the user device commanding it to wake up) orit may be part of a larger transmission comprising the gathered contextdata. Responsive to receiving, at 301, the wake indication, anembodiment may, at 303, wake the device from the low power mode. Onceawoken, an embodiment may, at 304, receive the gathered context data.Conversely, responsive to not receiving, at 301, the wake indication, anembodiment may, at 302, maintain the device in low power mode.

Once the context data is received, an embodiment may, at 305, perform anaction based on the context data. In an embodiment, the action may beone or more of a variety of different actions. For example, responsiveto receiving context data indicating that a user is within apredetermined distance from the device (e.g., 5 feet, 10 feet, in thesame room as the device, etc.), an embodiment may automatically activateone or more device components (e.g., a display screen, one or more inputdevices, etc.). In another, similar example, responsive to receivingcontext data indicating that a user has left the predetermined distance,an embodiment may automatically lock the device components. In yetanother example, responsive to receiving context data indicating thenumber of individuals participating in a conference call (e.g., a VoIPcall, etc.), an embodiment may adjust a microphone noise cancellationfield based on the number of participants (e.g., narrow field if onlyone participating participants, widen field if multiple participants,etc.). In yet a further example, responsive to receiving context dataindicating a user's identity, an embodiment may enable certain devicefunctions for authorized users (e.g., user profiles, protectedapplications, etc.) and/or lock or disable certain device functions forunauthorized users (e.g., login functions, setting functions,transaction functions, etc.). An individual having skill in the art mayrecognize that the examples provided above are not limiting and thatother actions, not explicitly mentioned and described here, may also beperformed.

In an embodiment, after a user device has performed an action based onthe context data, the user device may return back to the low power mode(e.g., immediately after the action is performed, a predetermined timeafter the action is performed, etc.). An embodiment may then remain inthe low power mode until another indication is received to wake up.

The various embodiments described herein thus represent a technicalimprovement to conventional context data gathering techniques. Using thetechniques described herein, a device in a low power mode may receivecontext data obtained from other connected IoT devices. Once the contextdata is received, an embodiment may wake the device and thereafterperform an action based on the context data. Such a method may allow adevice to understand context without requiring the addition of amicrocontroller that consumes battery power. Additionally, such a methodmay be utilized to leverage processing capabilities that may be evengreater than when the device is active and fully powered.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device that are executed by aprocessor. A storage device may be, for example, a system, apparatus, ordevice (e.g., an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device) or any suitablecombination of the foregoing. More specific examples of a storagedevice/medium include the following: a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a magnetic storage device, or any suitablecombination of the foregoing. In the context of this document, a storagedevice is not a signal and “non-transitory” includes all media exceptsignal media.

Program code embodied on a storage medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, et cetera, or any suitable combination of theforegoing.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made through other devices (for example, throughthe Internet using an Internet Service Provider), through wirelessconnections, e.g., near-field communication, or through a hard wireconnection, such as over a USB connection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products accordingto various example embodiments. It will be understood that the actionsand functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, a special purpose information handling device, or otherprogrammable data processing device to produce a machine, such that theinstructions, which execute via a processor of the device implement thefunctions/acts specified.

It is worth noting that while specific blocks are used in the figures,and a particular ordering of blocks has been illustrated, these arenon-limiting examples. In certain contexts, two or more blocks may becombined, a block may be split into two or more blocks, or certainblocks may be re-ordered or re-organized as appropriate, as the explicitillustrated examples are used only for descriptive purposes and are notto be construed as limiting.

As used herein, the singular “a” and “an” may be construed as includingthe plural “one or more” unless clearly indicated otherwise.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

What is claimed is:
 1. A method, comprising: receiving, at aninformation handling device in a low power mode, a wake indication;waking, responsive to the receiving, the information handling devicefrom the low power mode; receiving, at the awoken information handlingdevice, context data obtained by at least one other device; andperforming an action based on the received context data.
 2. The methodof claim 1, wherein the receiving comprises receiving at least one of:an indication of the action corresponding to the context data and a wakeinstruction.
 3. The method of claim 1, wherein the at least one otherdevice comprises a plurality of Internet of Things (IoT) devices.
 4. Themethod of claim 1, wherein the contextual data is processed by at leastone of: the at least one other device and a server associated with theat least one other device.
 5. The method of claim 1, wherein thecontextual data comprises position data for at least one user in alocation associated with the information handling device.
 6. The methodof claim 5, wherein the performing the action comprises adjusting acharacteristic of the information handling device responsive to theposition data indicating that the at least one user is within apredetermined threshold distance of the information handling device. 7.The method of claim 1, wherein the contextual data comprises identitydata for at least one user in a location associated with the informationhandling device.
 8. The method of claim 7, wherein the performing theaction comprises activating a security measure on the informationhandling device responsive to the identity data indicating that anon-authorized user is interacting with the information handling device.9. The method of claim 1, wherein the contextual data comprises activitydata engaged in by at least one user in a location associated with theinformation handling device.
 10. The method of claim 9, wherein theperforming the action comprises adjusting a characteristic of theinformation handling device responsive to the activity data indicating atype of activity engaged in by the at least one user.
 11. An informationhandling device, comprising: a processor; a memory device that storesinstructions executable by the processor to: receive, when theinformation handling device is in a low power mode, a wake indication;wake, responsive to the receiving, the information handling device fromthe low power mode; receiving, at the awoken information handlingdevice, context data obtained by at least one other device; and performan action based on the received context data.
 12. The informationhandling device of claim 11, wherein the instructions executable by theprocessor to receive comprise instructions executable by the processorto receive at least one of: an indication of the action corresponding tothe context data and a wakeup instruction.
 13. The information handlingdevice of claim 11, wherein the at least one other device comprises aplurality of Internet of Things (IoT) devices.
 14. The informationhandling device of claim 11, wherein the contextual data is processed byat least one of: the at least one other device and a server associatedwith the at least one device.
 15. The information handling device ofclaim 11, wherein the contextual data comprises position data for atleast one user in a location associated with the information handlingdevice.
 16. The information handling device of claim 14, wherein theinstruction executable by the processor to perform the action compriseinstructions executable by the processor to adjust a characteristic ofthe information handling device responsive to the position dataindicating that the at least one user is within a predeterminedthreshold distance of the information handling device.
 17. Theinformation handling device of claim 11, wherein the contextual datacomprises identity data for at least one user in a location associatedwith the information handling device.
 18. The information handlingdevice of claim 16, wherein the instructions executable by the processorto perform the action comprise instructions executable by the processorto activate a security measure on the information handling deviceresponsive to the identity data indicating that a non-authorized user isinteracting with the information handling device.
 19. The informationhandling device of claim 11, wherein the contextual data comprisesactivity data engaged in by at least one user in a location associatedwith the information handling device and wherein the instructionsexecutable by the processor to perform the action comprise instructionsexecutable by the processor to adjust a characteristic of theinformation handling device responsive to the activity data indicating atype of activity engaged in by the at least on user.
 20. A system,comprising: a plurality of connected devices configured to transmitcontext data to an information handling device in a low power mode,wherein the system is configured to: gather context data using theplurality of connected devices; wake, responsive to the gathering, theinformation handling device from the low power mode; send the contextdata to the awoken information handling device; and perform, using theinformation handling device, an action based on the received contextdata.